An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hey all, I am a first time publisher navigating the App Review process. I want to publish a watchOS only app, but keep getting this feedback: Regarding 4.0, Apple Watch app icon's background color is still black. Based on our investigation, you have included plain black icons. To resolve this issue, it would be appropriate to modify your app's Apple Watch app icon to include a lighter background color to ensure that it is recognizable and appears circular on Apple Watch. I set the following configs: Project -> Targets -> Apple Watch App -> App Icons & Launch Screen -> App Icon set to my Icon Composer file. Checked App Icons Source. I was able to install my build through TestFlight and successfully install on my watch, and the App Icon displays properly there. I also saw a recent Reddit post from another developer facing the same issue. I can't link that post, but will share this post with the OP. I attached what the reviewer sent me with the rejection.

Dear App Review Team, Our app – Apple ID 6754872058 has been stuck in the “In Review” status for over 7 days (since Jan, 15 at 10:44 PM). Normally, reviews begin within a few days, but in our case, it seems unusually delayed. Could you please clarify: • Is there a specific reason for this hold? • Is any action required from our side? • When can we expect the review to finish? Thank you very much for your time and assistance.

I'm extremely frustrated with Apple's unfair app review process. To make a long story short, for every app I've ever submitted, Apple has made false accusations about problems with my apps. Some of their feedback has absolutely been legitimate and correct, which I appreciate, but I would say about 50% of all "feedback" I've ever received has turned out to be objectively wrong. In some cases, the App Review team's gaslighting has been so strong that I have had to submit screenshots of code as proof that their accusations were completely wrong, after which they have had to accept the app. In one instance, they have claimed that one of my apps would not be allowed on the App Store at all, and when I link to multiple other apps that works EXACTLY the same way, the App Review team love to point out that you are not allowed to compare yourself to other apps. To be clear, I'm an indie developer and I'm not even comparing myself to apps from large corporations or any popular apps at all (since it's well known they get the VIP treatment), all apps I have compared myself to are from small, unknown indie developers such as myself - so I'm only comparing myself to developers in the same category as me. Telling developers that they are not allowed to compare themselves to other developers is VERY ethically problematic, imagine doing that to minorities in real life. I'm a minority in multiple ways, and I'm very worried about the ethics and moral at the App Review team. When I ask why they reject my app, but approve many apps that were recently released that works EXACTLY the same way as my app, I either get no reply at all or they tell me that I can't compare myself to others. Submitting appeals to the App Review Board doesn't help either. To be completely transparent with you, it has been very hard and draining on my mental health to have this invisible wall consisting of gaslighting that the App Review team has set up for me. It just doesn't make sense... The app review process is unfair, inconsistent and problematic, and it should be a serious eyebrow-raiser when Apple's App Review team can't explain why some small indie developers get approved easily while others get rejected. Especially since it seems like the pattern is that those who get rejected are humans in various kinds of minorities, as evidences by some other threads on this topic.

Hi, Anyone else hitting this App Store Connect issue? I have now submitted two app versions. Both get accepted and I can release them, but the subscriptions are never included. What is happening: App versions get approved normally No “In-App Purchases” section appears on the app version review page Subscriptions page shows subscriptions stuck on “In Review” for 10 days Subscription localization is “Rejected” and completely locked I cannot edit, recreate, or resubmit anything related to subscriptions.. Tried submitting a new app version again, same result. App approved, subscriptions still stuck. So I keep releasing without subscriptions every time 🤦‍♂️ Anyone experienced this or found a way to unblock subscriptions when localization is rejected and locked? Thanks!

Did any one face this issue "Note that users expect apps they download to function on all the devices where they are available. Since your app may be downloaded onto iPad devices, it is important that it also function as expected for iPad users" even though we already done the following Target → General → Deployment Info Devices: ☑ iPhone ☐ iPad ← MUST be unchecked UIDeviceFamily = 1 Mac Catalyst is set to NO

Hello everyone, I'm seeking advice from the community regarding an App Review rejection I've been struggling with. Situation: My Mac app, an application launcher, has been rejected under Guideline 5.2.5 for being "too similar to LaunchPad, which creates a misleading association with Apple." After requesting specific feedback on what needs to change, I received only a generic response directing me to read the guidelines without any actionable details about which features or design elements are problematic. My App's Differentiating Features: My app includes numerous features that distinguish it from LaunchPad: Windowed mode in addition to fullscreen Category topbar with filtering capabilities Resizable grid with customizable icon sizes and spacing Advanced organization with custom categories, tags, and usage tracking Different visual design language and interaction patterns The Challenge: I've observed several other app launchers on the Mac App Store that appear to share more similarities with LaunchPad than mine does (e.g., identical pagination, similar grid layouts, similar visual design). This makes it difficult to understand why my app specifically was flagged. What I've Tried: Provided detailed documentation of differentiating features Requested specific feedback on which elements need changing Compared my app to approved alternatives on the store Received only a generic response with no actionable guidance Questions for the Community: Has anyone else faced this type of rejection for app launchers or similar utility apps? What specific changes did you make that satisfied App Review? Are there particular visual elements or features that App Review considers "off limits" for this category? Should I consider filing a formal appeal, or is there a better path forward? Are there any Apple engineers who might be able to provide insight into how to differentiate from built-in macOS apps while still solving the same user problem? My Goal: I'm not trying to clone LaunchPad - I'm trying to provide users with a more powerful, customizable alternative. However, without specific guidance on what crosses the line, I'm stuck in a loop where I can't make meaningful changes. Any advice, experiences, or suggestions would be greatly appreciated. Has anyone successfully navigated a similar rejection? Thank you in advance for your help!

Hello, I submitted my game app on 28 Dec last year. Unfortunately, it was stuck in review for weeks. I've tried submitting a request to expedite the review, I've reached out via the contact form, I've even tried resubmitting the build - all to no avail. Prior to this, I've been able to release monthly updates without trouble. Any advice on this issue would be greatly appreciated, thank you kindly!

Hi everyone, We’re looking for advice regarding an App Store review rejection and would really appreciate insights from developers with similar experience. Our app is a retro game emulator platform. It provides emulator functionality only (e.g. NES / GB / GBA emulation) and does NOT include, bundle, or download any game ROMs. Key points about our app design: ❌ No ROMs are bundled or distributed ❌ No in-app ROM downloads ✅ Users can only import their own ROM files that they legally own (e.g. personal backups) ✅ No copyrighted game names, box art, screenshots, or branding are used ✅ The app is positioned as a general-purpose emulator tool, similar to a media player that plays user-provided files However, during review we received the following rejection: The app appears to contain copyrighted video game files. Apps and their content should not infringe upon the rights of another party… We’re confused about what might have triggered this decision and would appreciate guidance on: On what basis Apple may conclude that the app “contains” copyrighted game files? Could this be related to: App screenshots or preview videos? Default demo flows or UI text? The emulator functionality itself? What changes are typically required to pass review, such as: Adding stronger legal disclaimers Requiring user confirmation that imported ROMs are legally owned Removing any potentially misleading UI wording Explicitly clarifying ROM ownership responsibility We’ve noticed that similar emulator apps already exist on the App Store, so we’re trying to understand: Whether there is a clear compliance path What modifications have worked for other developers in similar cases Thanks a lot in advance for any advice or shared experience 🙏 Happy to provide more details if needed.

Hello everybody, I have a never ending issue with appstore review, an need a QUICK HELP ! I am submitting a new app (oral training), for Iphones only. I disabled other devices (such as Ipas) via Xcode. In the appstore informations form, it is obligatory to provide ipad screens, so I provided screens showing Iphone experience. Appstore team asked me to remove it because I don't authorize Ipads. But if I remove those screens, form cannot be sent. I don't understantd how to proceed. Thanks for the help Regards Jean

I just launched my app Stonk on the App Store and spent $100 on ads but haven’t seen any downloads. I’m curious if others rely on the same strategies or if bigger ad budgets work better. Marketing has been challenging, so I’d appreciate advice on how to advertise more effectively.

Hello everyone, We received a Pending Termination Notice on Nov 4, 2025, flagging our developer account for removal under Section 3.2(f) of the Apple Developer Program License Agreement. The notice alleged that our app submissions "repeatedly violated the App Review Guidelines in an attempt to evade the review process." We unequivocally state that there was no intent to evade review or act dishonestly. The repeated submissions were actually a result of our efforts to resolve a trademark dispute regarding our app icon with a third party. We were in active legal negotiations to update our assets to a compliant design. The resubmissions were attempts to update the metadata to comply with these legal requests. Unfortunately, this overlapped with the App Review process and created the appearance of "evasion." Case Details: Case Number: 102748595474 App ID: 1599464287 Notice Date: Nov 4, 2025 Current Status: Appeal submitted; awaiting review. What we've done so far **Legal Resolution:** We are now in the final stages of a legal settlement with the third party. We have obtained a statement from our legal counsel and evidence of this settlement to demonstrate our Good Faith and commitment to the App Store Guidelines. **Appeals Submitted:** We have diligently followed standard procedures and submitted three formal appeals, with the latest one submitted on Nov 22. **Support Contact:** We have contacted Developer Support multiple times via email to follow up. Questions: * Given the expiration of the termination deadline, is there any way to confirm if our account is safe from automatic removal while the review is ongoing? * Are there any additional steps we should take to bring this to the App Review Board's attention? * Is there any other documentation we should submit to expedite the process? The 30-day appeal window ended on Dec 4, and this deadline has now passed. We are deeply concerned that our account may be automatically terminated despite our full cooperation and pending appeal. Having been a dedicated developer for over 8 years, we are eager to resolve this amicably. Thank you for your time and assistance.

I was wondering if there was a way to submit an app for review before completing the terms of service and privacy policy in case the app does not get approved.

I built the Appvector tool – aso.report, a completely free ASO analysis platform designed to help indie developers easily improve their App Store listings without complex metrics or costly subscriptions. Just paste your app’s URL to get instant insights, multi-country analysis, and actionable recommendations - making ASO simple, accessible, and effective for everyone.

Hey everyone, I’ve been building iOS apps since 2011, released several, took a four-year break, and recently launched two new apps, but the ecosystem feels very different now. Earlier, new apps saw strong first-day downloads and fast Google indexing, while today my App Store pages took weeks to appear and show almost no organic traction without promotion, so I’m curious if others notice this and how developers now gain discovery.

App store growth in 2026 is driven by discoverability that blends relevance conversion and long term quality signals as Apple and Google now understand intent user satisfaction and app value far beyond keywords and installs. This guide explains how modern app ranking works how to track it and how to improve visibility on iOS App Store and Google Play using strategies aligned with today’s algorithms and user behavior.

Hello everyone, My team is exploring the implementation of an Apple Wallet pass for a loyalty program linked to a brand in an age-restricted product category. The intended use cases for the Wallet pass are: Member identification at events — Quick verification at brand events or exclusive venues, with tier-based perks (e.g., priority entry for higher tiers) Support services — Members present their card at retail locations to receive assistance Tier and points display — Dynamic visual changes based on loyalty level and current points balance Notifications — Pass updates for expiring points, upcoming events, or relevant announcements The pass would function as a standard Store Card (membership/loyalty) — no payments, no stored value, just identification and informational display. Before investing development effort, I'd like to understand: Has anyone successfully implemented Wallet passes for brands in restricted categories (tobacco, alcohol, etc.)? Are there specific guidelines or restrictions I should be aware of beyond the standard Wallet documentation? Is there a recommended channel to get official guidance from Apple on eligibility before building? Any insights or experiences would be appreciated. Thanks!

I am developing a utility application for macOS. In the next version, I would like to access data files from multiple third-party web browsers. However, requiring users to manually select and grant access to each browser’s folder individually would be inconvenient from a usability perspective. Therefore, I am considering requesting Full Disk Access for my app. Is it realistic to expect App Store review approval when requesting Full Disk Access? Under what conditions or use cases is such permission typically accepted by Apple? I would greatly appreciate any advice or experiences you can share.

Hello, I have an app with a few essential asset packs currently totaling to ~8GB. I've noticed that when trying to install the app fresh from TestFlight, there is a significant delay between tapping install and the app appearing on the device in the loading state. The delay is long enough where it's hard to tell what's happening, or if the installation has failed. This also appears to be an issue in App Review, as I've had my app rejected twice due to the app not loading on the reviewers device. The reason they gave is UIRequiredDeviceCapabilities is blocking the installation, but UIRequiredDeviceCapabilities is empty. Note: I'm not looking for App Store review help, simply sharing the extent of the issue. Thank you

Mobile app marketing feels even more challenging in 2026, with once-reliable tactics like paid installs, influencer promotions, and push notifications losing impact while organic growth and user retention continue to slow. I am curious what is truly working for developers in 2026, whether stronger ASO, community-led engagement, web-to-app funnels, or long-term retention strategies are outperforming traditional paid acquisition.

Hello everyone, I’m looking for guidance regarding a prolonged App Store review delay. I submitted my app for review more than 12 days ago, and its status has remained “Waiting for Review” with no updates. I have also tried contacting Apple through App Store Connect and the Contact Us option, but I haven’t received any response so far. This app does not include any unusual features, private APIs, or sensitive content, and previous versions (or similar apps) were reviewed much faster. The long delay is blocking a planned release and affecting our timeline. Could anyone please advise: If this review duration is normal lately? Whether there is a recommended escalation path beyond App Store Connect messages? If there are any known review backlogs or issues I should be aware of? Any insights or suggestions from developers who’ve faced a similar situation would be greatly appreciated. Thank you for your time and help.